The MDM server application must generate unique session identifiers with organization defined randomness requirements.

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
V-36356	SRG-APP-224-MDM-291-SRV	SV-47760r1_rule		Low

Description
This requirement focuses on communications protection at the application session, versus network packet level. The intent of this control is to establish grounds for confidence at each end of a communications session in the ongoing identity of the other party and in the validity of the information being transmitted. This helps prevent a session hijacking attack.

STIG	Date
Mobile Device Manager Security Requirements Guide	2013-01-24

Details

Check Text ( C-44598r1_chk )
Review the MDM server configuration to determine whether the MDM server generate unique session identifiers with organization defined randomness requirements. Determine how the MDM server generates the session identifier. Have an administrator log into the server and view the logs to verify a unique session identifier was assigned to the session. If the MDM server does not generate unique session identifiers with organization defined randomness requirements, this is a finding.

Check Text ( C-44598r1_chk )

Review the MDM server configuration to determine whether the MDM server generate unique session identifiers with organization defined randomness requirements. Determine how the MDM server generates the session identifier. Have an administrator log into the server and view the logs to verify a unique session identifier was assigned to the session. If the MDM server does not generate unique session identifiers with organization defined randomness requirements, this is a finding.

Fix Text (F-40888r1_fix)
Configure that MDM server to generate unique session identifiers with organization defined randomness requirements.